Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"Unexpected Vcloud director error {{0}}" error when creating replications in VMware Cloud Director Availability 4.x (78649)

Last Updated: 8/12/2020Categories: TroubleshootingTotal Views: 4389Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Configuring a replication from an On-Premises site to a Cloud site fails with the error:

[ object object ]

Configuring a replication from a Cloud site to an On-Premises site fails with the error:

Unexpected Vcloud director error {{0}}

In /opt/vmware/h4/cloud/log/cloud.log on the Cloud Replication Management Appliance, you see similar messages to:

2020-04-13 14:46:05.709 ERROR - [UI-c0d24aab-7645-42a9-8383-bd454148b022-F2] [https-jsse-nio-8443-exec-4] c.v.h.c.c.error.ExceptionAdvisorBase     : A GET request from User@VMware [10.10.10.10] to /inventory/vapps?sort=&offset=0&limit=20&site=VMware failed.
com.vmware.vcloud.client.exception.VcloudException: HTTP Response code: 414
at com.vmware.vcloud.client.VcloudClient.lambda$defaultErrorDeserializer$0(VcloudClient.java:195)
at com.vmware.rest.client.AbstractRestClient.convert(AbstractRestClient.java:215)

In /opt/vmware/h4/cloud/log/request.log on the Cloud Replication Management Appliance, you see similar mesages:

2020-04-14 13:22:33.017 TRACE - [d7ad86ed-70e0-4813-bdfa-7216e73f791a] [c4-scheduler-2] c.vmware.rest.client.AbstractRestClient  : Request to GET https://<vcd_fqdn>/api/query?type=adminOrgVdcStorageProfile&format=idrecords&offset=0&pageSize=100&filter=(vdc==0045bc43-fe3e-4588-adc7-051ba6f94622,vdc==012b5624-1595-4b09-8c9a-6a660ad938bd,vdc==02aa907d-98d8-47a5-b39e...
2020-04-14 13:22:33.018  WARN - [d7ad86ed-70e0-4813-bdfa-7216e73f791a] [c4-scheduler-2] c.vmware.rest.client.AbstractRestClient  : The HTTP response has no body. Code = 414, reason =

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

The issue occurs because the HTTP request send from Cloud Director Availability to vCloud Director has a header larger than 8KB.

The default supported HTTP header is 8KB for Apache. When the header exceeds this value the query times out, Cloud Director Availability is unable to fetch the resources from vCloud Director and no response is returned.

When limiting the accessible Provider VDCs in Cloud Director Availability, the HTTP header size is determined by the number of Organization VDCs that Cloud Director Availability has access to. The maximum amount of Organization VDCs that a single Cloud Director Availability instance can handle in this configuration is ~164, this number can vary depending on the length of the vCloud Director URL.

Resolution

This is a known issue affecting VMware Cloud Director Availability 4.x.
Currently, there is no resolution.

Workaround

To work around this issue, modify the accessible Provider VDC setting in the Cloud Director Availability Provider Portal to change how the vCloud Director API request header is built.

Navigate to the Cloud Director Availability Provider Portal.

Log in with either as root or a vCloud Director System Administrator user.

In the left pane, click Configuration.

Under Site details, next to Accessible Provider VDCs, click Edit.

Select VMware Cloud Director Availability can access all Provider VDCs and click Apply.

If you cannot give Cloud Director Availability access all Provider VDCs because your vCloud Director instance contains Provider VDCs that are backed by vCenter Servers under different Single Sign-On domains or because this would go against the supported configuration limits, you can limit the amount of  Organization VDCs that a single Cloud Director Availability instance handle by deploying more Cloud Director Availability instances on your environment.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Availability

Related Versions:

VMware vCloud Availability 3.5.x

VMware vCloud Availability 3.0.x

VMware Cloud Director Availability 4.x

Take Our Survey

Support Assistant